Next: Archiving, Previous: Protocols, Up: Capture - Refile - Archive [Contents][Index]
When reviewing the captured data, you may want to refile or to copy some of the entries into a different list, for example into a project. Cutting, finding the right location, and then pasting the note is cumbersome. To simplify this process, you can use the following special command:
org-copy)Copying works like refiling, except that the original note is not deleted.
org-refile)Refile the entry or region at point. This command offers
possible locations for refiling the entry and lets you select
one with completion. The item (or all items in the region) is
filed below the target heading as a subitem. Depending on
org-reverse-note-order, it will be either the
first or last subitem.
By default, all level 1 headlines in the current buffer are
considered to be targets, but you can have more complex
definitions across a number of files. See the variable
org-refile-targets for details. If you would
like to select a location via a file-path-like completion
along the outline path, see the variables
org-refile-use-outline-path and
org-outline-path-complete-in-steps. If you would
like to be able to create new nodes as new parents for
refiling on the fly, check the variable
org-refile-allow-creating-parent-nodes. When the
variable org-log-refile96 is set, a timestamp
or a note will be recorded when an entry has been refiled.
org-refile-goto-last-stored)Jump to the location where org-refile last
moved a tree to.
Refile as the child of the item currently being clocked.
Refile and keep the entry in place. Also see
org-refile-keep to make this the default
behavior, and beware that this may result in duplicated
ID properties.
org-refile-cache-clear)Clear the target cache. Caching of refile targets can be
turned on by setting org-refile-use-cache. To
make the command see new possible targets, you have to clear
the cache with this command.
Next: Archiving, Previous: Protocols, Up: Capture - Refile - Archive [Contents][Index]